Select Framework Architecture

The Framework installation includes three separate components, each with its own setup executable:

• Database Components
• Website Components
• Application Components

This separation allows the Framework installation to be spread across more than one server. The chosen architecture varies from customer to customer. The Hardware and Software Requirements document will help you decide the best architecture for your environment.

Create Service Account

The Framework requires a service account to run many components of the installation. The following are configured to run as the service account:

• Anonymous requests in IIS
• COM+ application
• Scheduled tasks
• Database access (if using a trusted connection)

A domain account must be created by a network administrator. This domain account must be created before the Framework can be installed. This user should have the following properties:

• User cannot change his or her password.
• The password never expires.
• User should be given access to log on the network 24 hours per day.
• If two domain accounts are used for separate servers, both accounts must be added to the admin group in the Web Server.

Permissions for this user are very limited. All required permissions are documented in the Setting Permissions section (see below).

Create Share Directory

A directory accessible to the Web and Application Servers must be created. The Framework stores various documents in this directory, and will grow in size over time. The following are items that the Framework will store in this directory:

• Archived import and export files
• Credit reports
• Skip Trace reports
• Documents uploaded through the Framework
• Log files

This directory should not be created on a drive with limited space available.

Install Required Software

Ensure all required software is installed on the Framework servers. Refer the following documents for more information:

• Akcelerant Framework Software Requirements
• Installing and configuring IIS 8 on Windows Server 2012
• Installing and configuring Reporting Services (KB-211439)

64-bit Windows Server Support

With the release of Version 10 of the Akcelerant Framework, 64-bit Windows Server Operating Systems are now supported including Windows 2003, Windows 2008, Windows 2008 R2 and Windows 2012. Please review the section on “Configuring your 64-bit server for the Akcelerant Framework” for additional steps to perform after initial installation.

Windows Server 2012 Prerequisite Software Installation

• If the server uses Windows Server 2012 as its operating system, then the following components must be installed:
• Make sure the Component Services is installed. To check this go to Control Panel>All Control Panel Items>Administrative Tools>Component Services menu should be in the list.

• Click Component Services the following screen should be displayed:

• Make sure the following IIS8 roles are installed.  Under Application Development make sure ASP role is installed.

This IIS role is not selected by default when installing IIS roles for the Windows Server 2012 and can be easily missed. To verify the settings go to Control panel> Program and Features>Turn Windows feature on or of>Next.

• Under Security make sure Basic and Windows Authentication are installed
• Under Management Tools make sure IIS 6 Management Compatibility components are installed
• Verify Framework 3.5 Installation is selected

Prerequisite Software Installation

Before the Framework software is installed, there are prerequisite software application that must be installed.  These are:

Prerequisite Software	How to Install
ASP.net MVC 1.0	Download ASP.net MVC 1.0 from this URL and install with all default options: http://www.microsoft.com/downloads/details.aspx?FamilyID=53289097-73ce-43bf-b6a6-35e00103cb4b&displaylang=en Once installed, you will need to register the MVC pages extension in IIS: Browse to the following file and double-click it to install the page extension: [Program Files]\Microsoft ASP.NET\ASP.NET MVC 1.0\Scripts\registermvc.wsf This script will not provide any confirmation of completion. Unless you receive an error, you can assume it was successful within seconds after running it. Reset IIS now by clicking on your server’s START button >Run and then enter the word iisreset and hit ENTER. A small window will pop open briefly and confirm that IIS is stopping and restarting. Installation is now complete.
Credit++4..0.0.22	If you have any previous versions of Credit ++ installed on your server, you should uninstall them first. Go to Start >Control Panel >Add/Remove Programs. Locate any entries for “Credit ++ Toolkit” and remove them. A reboot may be required. The installation file for Credit ++ 4.0.0.22 is bundled with your “10.2.1.zip” file and is named “install400-22BASIC.exe”. Extract this file from the zip file and save to any available folder on your hard drive. Browse to the file and double-click it to begin the installation. Choose all default options and complete installation.

The database components must be installed before other Framework components are installed. The database components setup executable is not required to be run on the actual SQL Server. It is recommended that database installs are run from the Web or Application Servers. The database components setup executable will perform the following functions:

• Create the Framework database on the SQL Server you specify.
• Grant the service account access to the database and associate it to the proper security roles.

The following will explain each screen of the Installation Wizard.

• Choose the folder to install to and click the Next button.
• Every install and upgrade will generate SQL log files in the installation directory.

• Enter the name of the SQL Server where the Framework database will be created.
• The credentials required here are for connecting and creating the database. These credentials are not used for operation of the Framework application. By default, the application will use a trusted connection with the service account. This can be changed after the installation through the Framework Server Management application.

• Enter the name of the Framework database.
• Enter the Username of the Framework service account. The installer will add the service account as a SQL Server login and grant it required security roles in the Framework database.
• Enter the location where the SQL Server files should be stored. By choosing the Default location option, the install program will store these files in the folder the SQL Server was installed to.

If you would like to store these files in another location, enter the full path in the provided text boxes. You may choose to store the log file (.ldf) in a different location than the data file (.mdf).

• If you supply file locations, ensure the paths are valid and relative to your SQL Server. No validation is performed on these paths before the installation begins.

This step may take more than 10 minutes. SQL profiler tool can be used to monitor the SQL Server activities of running scripts.

The website components setup executable will perform the following functions:

• Create an IIS virtual directory
• Create an IIS application pool
• Create a COM+ application
• Configure Reporting Services
• Register Framework assemblies

The following will explain each screen of the Installation Wizard.

• Choose the folder to install to and click the Next button.
• The installation folder will store the website files and associated assemblies.

• Choose a website where the Framework virtual directory will be created.
• Enter the name of the virtual directory to create.
• If you require SSL in the Framework, select the “https://” option from the dropdown. Otherwise, leave the “http://” option selected.
• Enter the virtual path. The virtual path is the URL that users would use to gain access to the
• Framework application. For instance:
  • If installed under the Default Web Site, the Web Server machine name is TESTSERVER, and Akcelerant is the virtual directory name, the virtual path would be: TESTSERVER/Akcelerant/
  • If installed under a website named www.myserver.com, and Akcelerant is the virtual directory name, the virtual path would be: www.myserver.com/Akcelerant/
• Enter the name of the server where Reporting Services is installed.
• Enter the name of the folder where the Framework will store all of its Reporting Services reports.
• Check the SSL checkbox if your Reporting Services installation requires SSL.
• Click the Test Connection button to verify the information entered is correct.

• Enter the name of the COM+ application name
• Enter the Framework service account.  You must enter the Username in the format: DOMAIN/username.  Take caution when entering these credentials, as an incorrect Username or Password will cause the installation program to fail.

• Enter the SQL Server where the Framework database was installed.
• Enter the name of the Framework database.
• The credentials required here are used to update the database with entered configurations. These credentials are not used for operation of the Framework application. By default, the application will use a trusted connection with the service account. This can be changed after the installation through the Framework Server Management application.

The application components setup executable will perform the following functions:

• Create a COM+ application
• Register Framework assemblies
• Create Process Manager scheduled task

The following will explain each screen of the Installation Wizard.

• Choose the folder to install to and click the Next button.

• The installation folder will store the executable files and associated assemblies.

• Enter the SQL server where the Framework database was installed. Enter the name of the Framework database.
• The credentials required here are used to update the database with entered configurations. These credentials are not used for operation of the Framework application. By default, the application will use a trusted connection with the service account. This can be changed after the installation through the Framework Server Management application.

• Enter the location of the share directory. The share directory was created in the Pre-Installation section.
• Enter the Framework service account. You must enter the Username in the format: DOMAIN\username. Take caution when entering these credentials, as an incorrect Username or Password will cause the installation program to fail.

Configuring your 64-bit server for the Akcelerant Framework

In order for the Akcelerant Framework to work properly on a 64-bit Windows server, the server needs to be configured for 32-bit application support in IIS 8.

Enabling 32-bit application support on IIS 8

• If you’re running IIS 8, do the following:
• Open IIS (Control Panel > Administrative Tools > Internet Information Services).
• Expand the host computer and click on Application Pools.

• Locate the application pool that is running the Framework and right-click and select Advanced Settings.

• Change Enable 32-bit Applications to True

• The .NET Framework Version is set to 4.0 and the Managed Pipeline Mode Classic

Disabling User Access (UAC)

• To use the Akcelerant Server Manager tool on a 64-bit server, UAC needs to be disabled. Follow these steps to do so:
• Click Start, and then click Control Panel.
• In Control Panel, click User Accounts.
• In the User Accounts window, click Change User Account Control setting.
• In the User Account Control Setting tasks window, Change the bar to the lowest position.

• Then Click Yes in the following window.

Troubleshooting if IIS has problems

MVC Page Extensions Correctly Installed

Additional Steps for Windows 2012

• After installing Framework on a server with Windows 2012, the following needs to be verified for the application to function properly.
• Open Component Services manager found under Control Panel>System and Security>Administrative Tools (see below screenshot).

• Click on Computers then My Computer.
• Open COM+ Application folder.
• Double-click on the Akcelerant COM+ application and select Components folder.
• Select COM+ object from the list, right-click and click on Properties.
• Click on Advance tab and check the “Allow IIS intrinsic properties” check box if it is unchecked.

• Click OK.  This needs to be done for all COM+ objects in order for the Akcelerant COM+ object function properly

This must be done primarily for ASP pages to function properly with the COM+ object as well for the ASPX pages that still communicate with the COM+ object.

Invalid Reporting Services Configurations

A number of factors can contribute to errors while the installer is configuring Reporting Services. Some of these reasons are:

• Invalid Reporting Services server name configured.
• Communication errors between the web server and the Reporting Services server.
• The SQL Server Reporting Services Windows service is not started.
• The Reporting Services installation did not use the default name for the Report Server virtual directory.

Errors with Reporting Services are treated a little different than other installation errors. The installation process will display the error, but explain that the process will still continue the installation. Reporting Services should be configured manually if this occurs.

• This message explains that an error occurred, but the installation will continue:

• This is an example error message:

Windows Authentication Does Not Work

If windows authentication does not work after installation, a change to IIS may be required. The following should be configured in IIS to allow windows authentication to perform correctly.

• Disable anonymous access for the session \AuthenticateWindows.aspx.
• Configure the site, Session\AuthenticateWindows.aspx to have Anonymous Access and Integrated Windows Authenticate, except for the bullet item above.

Application Server Do Not Work with Framework 4.0 - Service Model Error

If the application services of Framework 4.0 do not work with Service Model Error (see screenshot below) after installation, it can be fixed by enabling all options under Windows Feature>IIS>Framework 4.5 and 3.

Application Service Do Not Work with Framework 4.0 - HTTP Error 404.17

The application services of Framework 4.0 do not work with 404.17 Error after installation (see screenshot below):

It can be fixed with the following command:  c:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe -i

If it still does not work, please make sure that the application pool for the service has the following settings:

Setting Permissions

The Framework service account must be granted proper permissions to the folders and files on the Framework servers.

Windows Temp Directory

The Framework uses COM Interop for some of its features. At runtime, the .NET Framework may create and execute files in the temp directory. Therefore, the service account must have full permissions on this directory. This is typically C:\Windows\Temp.

Share Directory

The share directory was created in the Pre Installation section. The service account must have the following permissions granted in the share directory:

• Modify
• List Folder Contents
• Read
• Write

Installation Directories

The following screenshot is accurate when all three components are installed on one server. If you installed to multiple servers, the installation directory name may be different between servers, but all directories under the Installation Directory will have the same name as this screenshot.

Set the following permissions on the installation sub-directories:

Exe	Read & Execute List Folder Contents Read
Temp	Modify List Folder Contents Read Write
Dll	Read & Execute List Folder Contents Read
Website	List Folder Contents Read

Setting Process Notifications

All of the Akcelerant Framework processes can be set up to use email notifications. You can set these processes to email one or more recipients when the process finishes with success, finishes with failure or enters wait mode.

Furthermore, two types of email notifications can be sent. The first type is internal email. This type of email will include technical information if a process fails. Internal email is designed to be sent to technical personnel. The second type is external email. This email excludes the technical information and is designed to be sent to business personnel.

We highly recommend that you set up email notifications. However, if you are not using SMTP, or do not want email notifications, skip to the next section. By default, all email notifications are turned off when the Framework is installed.

To activate internal emails when a process finishes with failure, perform the following:

• Open SQL Server Management Studio.
• Drill down and locate the Views folder in the Akcelerant database.
• Open the view named DB_SETTINGS_EMAIL_FAIL_INT. You will see the following:

• For each process that you want to send an internal email, change the “Email on Failure?” column to True. If you do not want an internal email sent, leave this column as False.
• Enter the recipient’s email address in the “Email Address(es)” column. To enter multiple email addresses, separate each email address with a semicolon (;).
• Repeat the above for every type of email notification you wish to receive. The following table lists each type and the name of the corresponding view in SQL Server Management Studio:

Email	Result Type	View Name
Internal	Success	DB_SETTINGS_EMAIL_SUCCESS_INT
Internal	Failure	DB_SETTINGS_EMAIL_FAIL_INT
Internal	Wait	DB_SETTINGS_EMAIL_WAIT_INT
External	Success	DB_SETTINGS_EMAIL_SUCCESS_EXT
External	Failure	DB_SETTINGS_EMAIL_FAIL_EXT
External	Wait	DB_SETTINGS_EMAIL_WAIT_EXT

Logging in as Administrator

You are now ready to use the Akcelerant Framework! At this point, the default user (Admin) is the only user in the system. You must log into the Framework as this user. Use the following information to access the site and log in.

• URL: defined in website component install
• Username: admin
• Password: admin

Once you log in, you will be required to change the password of the Admin user. Please do so, and keep this password in a safe place as the Admin is the only user in the system.

Navigate to System Management > Administrative Settings in the Framework. On the General tab, there are several fields that should be completed as part of the installation process.

Field	Description
Institution Name	Can be used on letters.
Institution Phone	Can be used on letters.
Institution Account Number	Used to communicate with the Akcelerant Software Extranet. This value must be obtained from Akcelerant.
Institution Account Password	Used to communicate with the Akcelerant Software Extranet. This value must be obtained from Akcelerant.
SMTP Server	The server name or IP address of your network’s SMTP server.
System Email Address	All emails sent by the Framework application will use this value as the “from address.”
Server Time Zone	The time zone of the actual servers where the Framework is installed.
Customer Time Zone	The time zone of the institution. This very rarely differs from the Server Time Zone.